-
Notifications
You must be signed in to change notification settings - Fork 250
feat(pulse-sdk-solidity): Create Pulse solidity SDK #2667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
// We can still generate ABIs with warnings, only throw for errors | ||
const errors = output.errors.filter((e) => e.severity === "error"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI i excluded warnings due to this warning in PythAggregatorV3.sol blocking the precommit for the Pulse SDK. Turns out there is no simple way to disable solc warnings for a single line/file 🙃
We should enforce warnings somewhere else anyway, probably turbo test:lint
and/or CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend you add the signatures for these as well. (you can use cast sig
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good call!
Summary
Scheduler
contract implements theIScheduler
interface from the SDK.abi_generator
script to handle non-path importsRationale
This makes it possible for other services and contracts to easily interact with the Pulse protocol and consume its ABIs.
How has this been tested?
Will manually test installing and using the package from NPM after this gets merged and published. Locally installing and using the SDK in contracts works fine.